Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e010dbcbf853819cf94bafb4fc8a10e177deae1f42103019dc72603f4c304692

Tx prefix hash: 9fa4d0bdb6b9c1de9617aad1e31d16245b05e6fb71f64554e61ae3d44e3efc16
Tx public key: 6477f61258ba4227c720e2c4ee1dd3f854cae5a0da2be15bcbc02e1e18ffbe9c
Timestamp: 1717285356 Timestamp [UCT]: 2024-06-01 23:42:36 Age [y:d:h:m:s]: 00:304:16:00:17
Block: 1035055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217740 RingCT/type: yes/0
Extra: 016477f61258ba4227c720e2c4ee1dd3f854cae5a0da2be15bcbc02e1e18ffbe9c02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1658673319f60bc5f9a84671da3dc03b14f4483c91a125d6a6079677ad2d5bad 0.600000000000 1503574 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": 1035065, "vin": [ { "gen": { "height": 1035055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1658673319f60bc5f9a84671da3dc03b14f4483c91a125d6a6079677ad2d5bad" } } ], "extra": [ 1, 100, 119, 246, 18, 88, 186, 66, 39, 199, 32, 226, 196, 238, 29, 211, 248, 84, 202, 229, 160, 218, 43, 225, 91, 203, 192, 46, 30, 24, 255, 190, 156, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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