Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b66cfe511a6a5af58431891348bdff6ae11164b98a462d7fd56640df84ea349

Tx prefix hash: 2a2a7d784ce8e5cda0676a88861324386f8b368836e6ad2f95d5af4d674ceb95
Tx public key: c37c97cdcd5b7a23664d8cd72a135ff3e8692567b9a8664d1a078cae92a1fb56
Timestamp: 1577036200 Timestamp [UCT]: 2019-12-22 17:36:40 Age [y:d:h:m:s]: 05:078:23:33:35
Block: 29695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205983 RingCT/type: yes/0
Extra: 01c37c97cdcd5b7a23664d8cd72a135ff3e8692567b9a8664d1a078cae92a1fb5602110000002e8a2ee0d9000000000000000000

1 output(s) for total of 489.338065506000 dcy

stealth address amount amount idx
00: 491de6826b0bee245f7ea1a65e195f1f3dda3a53e8ad12971328a46e2f9ac631 489.338065506000 48891 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": 29705, "vin": [ { "gen": { "height": 29695 } } ], "vout": [ { "amount": 489338065506, "target": { "key": "491de6826b0bee245f7ea1a65e195f1f3dda3a53e8ad12971328a46e2f9ac631" } } ], "extra": [ 1, 195, 124, 151, 205, 205, 91, 122, 35, 102, 77, 140, 215, 42, 19, 95, 243, 232, 105, 37, 103, 185, 168, 102, 77, 26, 7, 140, 174, 146, 161, 251, 86, 2, 17, 0, 0, 0, 46, 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