Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3253677b4ad39da2d50736e7be474056d79e2ee143dcebfd7a0519240a5e043

Tx prefix hash: bd06063218a64f84f8bd47f26cf95588c546b10b686386475b9ca5e6a909d6e2
Tx public key: b81347e844843afec9653dfbd515a6e77989d5b546031cee3550f2374e96ea05
Timestamp: 1632091370 Timestamp [UCT]: 2021-09-19 22:42:50 Age [y:d:h:m:s]: 04:046:16:11:45
Block: 337145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067710 RingCT/type: yes/0
Extra: 01b81347e844843afec9653dfbd515a6e77989d5b546031cee3550f2374e96ea0502110000006ff60c5d7e000000000000000000

1 output(s) for total of 46.870447044000 dcy

stealth address amount amount idx
00: b66ae2a5e185aa39dd22e7f9e171de2728b5aa3454c36be15a5ae01cc668e656 46.870447044000 694346 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": 337155, "vin": [ { "gen": { "height": 337145 } } ], "vout": [ { "amount": 46870447044, "target": { "key": "b66ae2a5e185aa39dd22e7f9e171de2728b5aa3454c36be15a5ae01cc668e656" } } ], "extra": [ 1, 184, 19, 71, 232, 68, 132, 58, 254, 201, 101, 61, 251, 213, 21, 166, 231, 121, 137, 213, 181, 70, 3, 28, 238, 53, 80, 242, 55, 78, 150, 234, 5, 2, 17, 0, 0, 0, 111, 246, 12, 93, 126, 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