Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e67c6c2b1c5640cfd2644af6ecf2ce2118aac6ce1df7ef7c160aa06e59903b1

Tx prefix hash: 9fb30a0e222d6a1da6d03149d626be04a2b93285ae9b52bf0172044b93a7881c
Tx public key: 0f7eafaeb883e385f8160a63f7fb328f993b00da0370d2665ba11c1bf20afe89
Timestamp: 1578017857 Timestamp [UCT]: 2020-01-03 02:17:37 Age [y:d:h:m:s]: 05:106:10:37:55
Block: 37516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1225911 RingCT/type: yes/0
Extra: 010f7eafaeb883e385f8160a63f7fb328f993b00da0370d2665ba11c1bf20afe890211000000098a2ee0d9000000000000000000

1 output(s) for total of 461.027795770000 dcy

stealth address amount amount idx
00: 4e7737bd08e7e216c0ca8faeeb97856aa95bbd829fec57022c7d4db43a9ef41f 461.027795770000 63720 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": 37526, "vin": [ { "gen": { "height": 37516 } } ], "vout": [ { "amount": 461027795770, "target": { "key": "4e7737bd08e7e216c0ca8faeeb97856aa95bbd829fec57022c7d4db43a9ef41f" } } ], "extra": [ 1, 15, 126, 175, 174, 184, 131, 227, 133, 248, 22, 10, 99, 247, 251, 50, 143, 153, 59, 0, 218, 3, 112, 210, 102, 91, 161, 28, 27, 242, 10, 254, 137, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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