Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 313757ba91af0e53e8919c3f2c63e6c92ce3216dd7aaa240c4916ea84480d2e7

Tx prefix hash: 30d4e88c4bcc40b0c10b07d621e1acc547980b7d7b4caeda18464b939eca5e47
Tx public key: e050cba32babad06eb8fb353aad2096c39b6fa427a76bdf835b2d0a46a8f10da
Timestamp: 1694746024 Timestamp [UCT]: 2023-09-15 02:47:04 Age [y:d:h:m:s]: 01:259:00:18:06
Block: 848370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446256 RingCT/type: yes/0
Extra: 01e050cba32babad06eb8fb353aad2096c39b6fa427a76bdf835b2d0a46a8f10da021100000005faf35c9c000000000000000000

1 output(s) for total of 0.948414257000 dcy

stealth address amount amount idx
00: e63e3f5ab208cfd8a210c2bd01dc852ad0c2bdfaf3890827d864f5100d3895a4 0.948414257000 1301968 of 0

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": 848380, "vin": [ { "gen": { "height": 848370 } } ], "vout": [ { "amount": 948414257, "target": { "key": "e63e3f5ab208cfd8a210c2bd01dc852ad0c2bdfaf3890827d864f5100d3895a4" } } ], "extra": [ 1, 224, 80, 203, 163, 43, 171, 173, 6, 235, 143, 179, 83, 170, 210, 9, 108, 57, 182, 250, 66, 122, 118, 189, 248, 53, 178, 208, 164, 106, 143, 16, 218, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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