Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d31838a87cbee0b7387f8ddd0e7d840dc4e7d240f2635b1446b6e0106c41471

Tx prefix hash: 649ebd87b3bb067991dfe27cd77011567e767c9dc03c803029e3ff8a1989a66a
Tx public key: f71cce8b08982bc3a0e2c8f70d80b870d9060c195fe2d426b3cba3ae3e62f842
Timestamp: 1609060267 Timestamp [UCT]: 2020-12-27 09:11:07 Age [y:d:h:m:s]: 03:327:04:20:31
Block: 170239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986177 RingCT/type: yes/0
Extra: 01f71cce8b08982bc3a0e2c8f70d80b870d9060c195fe2d426b3cba3ae3e62f8420211000003a1df1e48bb000000000000000000

1 output(s) for total of 167.466594503000 dcy

stealth address amount amount idx
00: a2fc3a5d5d2a46abe8b9896f4e847a388755bf39a25bd32df104ea1a4f5acfde 167.466594503000 318944 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": 170249, "vin": [ { "gen": { "height": 170239 } } ], "vout": [ { "amount": 167466594503, "target": { "key": "a2fc3a5d5d2a46abe8b9896f4e847a388755bf39a25bd32df104ea1a4f5acfde" } } ], "extra": [ 1, 247, 28, 206, 139, 8, 152, 43, 195, 160, 226, 200, 247, 13, 128, 184, 112, 217, 6, 12, 25, 95, 226, 212, 38, 179, 203, 163, 174, 62, 98, 248, 66, 2, 17, 0, 0, 3, 161, 223, 30, 72, 187, 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