Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48716ce91089cec3d55d73f546e634b268f56d349152afcb3b2d6948f6fe8530

Tx prefix hash: 640947b797146a95e0e7df53bd62d598d418d916dc6dda5b2c7405605a4743b6
Tx public key: 822bf81c6e4f6ebba1ef23240767f8610d2f357fda56a47767d50c11e5468f59
Timestamp: 1577913885 Timestamp [UCT]: 2020-01-01 21:24:45 Age [y:d:h:m:s]: 05:001:04:15:12
Block: 36629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150914 RingCT/type: yes/0
Extra: 01822bf81c6e4f6ebba1ef23240767f8610d2f357fda56a47767d50c11e5468f590211000000354943cd9f000000000000000000

1 output(s) for total of 464.123726038000 dcy

stealth address amount amount idx
00: 5383e950589d8c2e4de6b2ebc1e32bec5d8ede6a22122f3636326ff000da7cc3 464.123726038000 62093 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": 36639, "vin": [ { "gen": { "height": 36629 } } ], "vout": [ { "amount": 464123726038, "target": { "key": "5383e950589d8c2e4de6b2ebc1e32bec5d8ede6a22122f3636326ff000da7cc3" } } ], "extra": [ 1, 130, 43, 248, 28, 110, 79, 110, 187, 161, 239, 35, 36, 7, 103, 248, 97, 13, 47, 53, 127, 218, 86, 164, 119, 103, 213, 12, 17, 229, 70, 143, 89, 2, 17, 0, 0, 0, 53, 73, 67, 205, 159, 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