Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ce9cd81dadea4c8fa1a16b2cdec50e4ecb24e1e595ea18e013ec402a3d7602b8

Tx prefix hash: 7101769e51fa427b48dfb603cf6e5a9d0279bcbabc9906a351c1e2f4324d46de
Tx public key: ddd47e2ca77e48fedd33ceda2e69e84b2ced7bacdca17951d3b781af4c55e261
Timestamp: 1711512579 Timestamp [UCT]: 2024-03-27 04:09:39 Age [y:d:h:m:s]: 00:293:22:59:15
Block: 987214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210391 RingCT/type: yes/0
Extra: 01ddd47e2ca77e48fedd33ceda2e69e84b2ced7bacdca17951d3b781af4c55e26102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27d105b8ddf1b02e1a35d79709327c968cce5180d9151550b23d61d9f4a8df36 0.600000000000 1447455 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 987224, "vin": [ { "gen": { "height": 987214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d105b8ddf1b02e1a35d79709327c968cce5180d9151550b23d61d9f4a8df36" } } ], "extra": [ 1, 221, 212, 126, 44, 167, 126, 72, 254, 221, 51, 206, 218, 46, 105, 232, 75, 44, 237, 123, 172, 220, 161, 121, 81, 211, 183, 129, 175, 76, 85, 226, 97, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8