Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 012e301ca16c23e736f55209a66dc11e92ccf5ee721319ad6aa6026dfac31636

Tx prefix hash: 77df800132efa4b0c7c780992a65a92a45d8e1114c7cfb7a70a2c2aae510b93a
Tx public key: a2735be8481a6fe0d5807855dc4fb2f5dd9e4d2fcff56a2f6ae8581cb8339914
Timestamp: 1732720340 Timestamp [UCT]: 2024-11-27 15:12:20 Age [y:d:h:m:s]: 00:154:21:02:28
Block: 1162910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110511 RingCT/type: yes/0
Extra: 01a2735be8481a6fe0d5807855dc4fb2f5dd9e4d2fcff56a2f6ae8581cb8339914021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5c49f01ce0d35e6ee16f67c03b45baccb1434c225b420a31df9fcabf00bd93e 0.600000000000 1648573 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": 1162920, "vin": [ { "gen": { "height": 1162910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5c49f01ce0d35e6ee16f67c03b45baccb1434c225b420a31df9fcabf00bd93e" } } ], "extra": [ 1, 162, 115, 91, 232, 72, 26, 111, 224, 213, 128, 120, 85, 220, 79, 178, 245, 221, 158, 77, 47, 207, 245, 106, 47, 106, 232, 88, 28, 184, 51, 153, 20, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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