Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 780014d1aa5e9aecdc229dd16a8ec82653cde1f706647d1ef19642da5f3c317b

Tx prefix hash: 1fd65f17a61ff412629567a916923c49d74ca4618df882b493f43df9fbd0cfcf
Tx public key: c693c900d3ed16ec2c4cd6788b21af9e0ececc968fa944858088617acd3513e3
Timestamp: 1726571665 Timestamp [UCT]: 2024-09-17 11:14:25 Age [y:d:h:m:s]: 00:257:09:50:32
Block: 1112030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183844 RingCT/type: yes/0
Extra: 01c693c900d3ed16ec2c4cd6788b21af9e0ececc968fa944858088617acd3513e3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94dfad194f7c719b2b02637f36f10b3a2bca7f5d3f2eb9126fbbdafff717de48 0.600000000000 1591205 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": 1112040, "vin": [ { "gen": { "height": 1112030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94dfad194f7c719b2b02637f36f10b3a2bca7f5d3f2eb9126fbbdafff717de48" } } ], "extra": [ 1, 198, 147, 201, 0, 211, 237, 22, 236, 44, 76, 214, 120, 139, 33, 175, 158, 14, 206, 204, 150, 143, 169, 68, 133, 128, 136, 97, 122, 205, 53, 19, 227, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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