Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4a0c00aef1d24bb5fa40897ad3fe94e95b90258a0a92012378803d0b14ad127

Tx prefix hash: 1fa11eef3b0c8c74deb06a716aad979f5fb9edae717bc04848d73fcfcd840ab3
Tx public key: 1eb668c1683ca14d8ca6aaeac3291abddee47dabba17a42532c9ccc2d51f8953
Timestamp: 1722422970 Timestamp [UCT]: 2024-07-31 10:49:30 Age [y:d:h:m:s]: 00:257:22:24:39
Block: 1077638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184258 RingCT/type: yes/0
Extra: 011eb668c1683ca14d8ca6aaeac3291abddee47dabba17a42532c9ccc2d51f895302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04fda8a8c5725d54b3f4455aa19b2b222d1861b5f1ec32c962615f1a25c01eb 0.600000000000 1550193 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": 1077648, "vin": [ { "gen": { "height": 1077638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04fda8a8c5725d54b3f4455aa19b2b222d1861b5f1ec32c962615f1a25c01eb" } } ], "extra": [ 1, 30, 182, 104, 193, 104, 60, 161, 77, 140, 166, 170, 234, 195, 41, 26, 189, 222, 228, 125, 171, 186, 23, 164, 37, 50, 201, 204, 194, 213, 31, 137, 83, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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