Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54e310908ff1ca07f985303230585aa4a9c69e33eddb316afb6c7f0d761a7da8

Tx prefix hash: d007b0118608e97c2ae5621061efdf352e7d7902f14c0ca4ddb18b8154282457
Tx public key: a0c30667d794ea46254099737062e85cf4a418e6bc1ad3b15748a1c4a1344e5c
Timestamp: 1718605526 Timestamp [UCT]: 2024-06-17 06:25:26 Age [y:d:h:m:s]: 00:193:02:06:42
Block: 1045999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138173 RingCT/type: yes/0
Extra: 01a0c30667d794ea46254099737062e85cf4a418e6bc1ad3b15748a1c4a1344e5c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 096ffb032dc888b3806749185e4a4bf9822e7dfc7e06b376f2762e655e2c5a35 0.600000000000 1515734 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": 1046009, "vin": [ { "gen": { "height": 1045999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "096ffb032dc888b3806749185e4a4bf9822e7dfc7e06b376f2762e655e2c5a35" } } ], "extra": [ 1, 160, 195, 6, 103, 215, 148, 234, 70, 37, 64, 153, 115, 112, 98, 232, 92, 244, 164, 24, 230, 188, 26, 211, 177, 87, 72, 161, 196, 161, 52, 78, 92, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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