Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca886fa2879707ac2a04b03b055c54bf325d57599ec2a982d644235495ea5bd

Tx prefix hash: 8dc02a86726d2641a27e416f5a124a7504a364a4a1dcef874d8e126e41e1e777
Tx public key: b0587ae96b3adf2a7cbf567ea76b3f70e633359cb5d8773d7053b87d0424fda4
Timestamp: 1581937014 Timestamp [UCT]: 2020-02-17 10:56:54 Age [y:d:h:m:s]: 04:284:00:50:52
Block: 66576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095520 RingCT/type: yes/0
Extra: 01b0587ae96b3adf2a7cbf567ea76b3f70e633359cb5d8773d7053b87d0424fda402110000000c8a2ee0d9000000000000000000

1 output(s) for total of 369.323449877000 dcy

stealth address amount amount idx
00: 9d7a1eaac2aece318e974c11acb9a573b851f4db2abcb4a508e5fb0f1a15712c 369.323449877000 122667 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": 66586, "vin": [ { "gen": { "height": 66576 } } ], "vout": [ { "amount": 369323449877, "target": { "key": "9d7a1eaac2aece318e974c11acb9a573b851f4db2abcb4a508e5fb0f1a15712c" } } ], "extra": [ 1, 176, 88, 122, 233, 107, 58, 223, 42, 124, 191, 86, 126, 167, 107, 63, 112, 230, 51, 53, 156, 181, 216, 119, 61, 112, 83, 184, 125, 4, 36, 253, 164, 2, 17, 0, 0, 0, 12, 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