Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4aed20bf423193be89ac0a605ec92ebd9ca5c84023c9f3f87ba6be746b07a60

Tx prefix hash: 8e58717aafe7ebb10fe98b78aecf0a5de808e802b49a5c47341873181424a350
Tx public key: 8b7e4f11413fdf1a8c3844b11b63e09b046f31a1257f5f58278df8541f92c01e
Timestamp: 1609975792 Timestamp [UCT]: 2021-01-06 23:29:52 Age [y:d:h:m:s]: 04:032:04:39:07
Block: 175471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1038365 RingCT/type: yes/0
Extra: 018b7e4f11413fdf1a8c3844b11b63e09b046f31a1257f5f58278df8541f92c01e0211000000834ea414e5000000000000000000

1 output(s) for total of 160.921817429000 dcy

stealth address amount amount idx
00: de02e5b2e8a825140be88e4b7377a15e93098c0e0c9a1592167689646075594d 160.921817429000 335133 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": 175481, "vin": [ { "gen": { "height": 175471 } } ], "vout": [ { "amount": 160921817429, "target": { "key": "de02e5b2e8a825140be88e4b7377a15e93098c0e0c9a1592167689646075594d" } } ], "extra": [ 1, 139, 126, 79, 17, 65, 63, 223, 26, 140, 56, 68, 177, 27, 99, 224, 155, 4, 111, 49, 161, 37, 127, 95, 88, 39, 141, 248, 84, 31, 146, 192, 30, 2, 17, 0, 0, 0, 131, 78, 164, 20, 229, 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