Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d1879936cb1ac36e0d0bff9615b3b93e2f647d828c386e0b8ad157ac8a954b

Tx prefix hash: d7fe5d2cf7234866b650e1b00004aceda5431cc0fdf61fa22052bc080fe33a2f
Tx public key: 707d353a63a77e524b051a2148d8dc87809cea10491c9ae29c68bc4ee65df1ae
Timestamp: 1718470545 Timestamp [UCT]: 2024-06-15 16:55:45 Age [y:d:h:m:s]: 00:277:05:21:07
Block: 1044885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198113 RingCT/type: yes/0
Extra: 01707d353a63a77e524b051a2148d8dc87809cea10491c9ae29c68bc4ee65df1ae021100000003befa2d88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9be044740115e526cfd8ef8e8e322e9fb57b98e706f2bbcb0784c19ec4504e08 0.600000000000 1514314 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": 1044895, "vin": [ { "gen": { "height": 1044885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9be044740115e526cfd8ef8e8e322e9fb57b98e706f2bbcb0784c19ec4504e08" } } ], "extra": [ 1, 112, 125, 53, 58, 99, 167, 126, 82, 75, 5, 26, 33, 72, 216, 220, 135, 128, 156, 234, 16, 73, 28, 154, 226, 156, 104, 188, 78, 230, 93, 241, 174, 2, 17, 0, 0, 0, 3, 190, 250, 45, 136, 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