Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76520d29a4134e2515c1d413406b49f12ea8f39a323dfdc288ddb3c312ec719a

Tx prefix hash: 5ede2272d11768c210d293d4aea0bc2500fb28064653eb040066eb2a6ba11259
Tx public key: 5e1b9a901f4365345e3c71d80cfc72eddf0c3e2d375e0c2e990ca0a2430e85aa
Timestamp: 1574215097 Timestamp [UCT]: 2019-11-20 01:58:17 Age [y:d:h:m:s]: 05:008:20:26:35
Block: 12909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149504 RingCT/type: yes/0
Extra: 015e1b9a901f4365345e3c71d80cfc72eddf0c3e2d375e0c2e990ca0a2430e85aa02110000000166a80d00000000000000000000

1 output(s) for total of 556.196192383000 dcy

stealth address amount amount idx
00: b2f2a0cb59aa6811053c1a94866918b1a42287a7ea83e984c8aa20d50f274db3 556.196192383000 14781 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": 12919, "vin": [ { "gen": { "height": 12909 } } ], "vout": [ { "amount": 556196192383, "target": { "key": "b2f2a0cb59aa6811053c1a94866918b1a42287a7ea83e984c8aa20d50f274db3" } } ], "extra": [ 1, 94, 27, 154, 144, 31, 67, 101, 52, 94, 60, 113, 216, 12, 252, 114, 237, 223, 12, 62, 45, 55, 94, 12, 46, 153, 12, 160, 162, 67, 14, 133, 170, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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