Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2423a276ebf3ec27a89d9014ba75b5949ad4b4513edc20fca945fc90530f695d

Tx prefix hash: bb7195c2f8f4731f29676cbcacdb7fe8a7a6a2ceab7eeb47a4913341bbc325e9
Tx public key: a1b8bbb592cda5609ab71cc881cc6b5e80f9bf73250de794cde58bc6d3c3c413
Timestamp: 1722584177 Timestamp [UCT]: 2024-08-02 07:36:17 Age [y:d:h:m:s]: 00:292:19:44:09
Block: 1078978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209227 RingCT/type: yes/0
Extra: 01a1b8bbb592cda5609ab71cc881cc6b5e80f9bf73250de794cde58bc6d3c3c413021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3eafedbee1b85d0d923d6742a65b45d3f264de1d676b3747bd80cea5385a098 0.600000000000 1551737 of 15

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": 1078988, "vin": [ { "gen": { "height": 1078978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3eafedbee1b85d0d923d6742a65b45d3f264de1d676b3747bd80cea5385a098" } } ], "extra": [ 1, 161, 184, 187, 181, 146, 205, 165, 96, 154, 183, 28, 200, 129, 204, 107, 94, 128, 249, 191, 115, 37, 13, 231, 148, 205, 229, 139, 198, 211, 195, 196, 19, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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