Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee5d91abddebfcb6be97acabffb614f0daf1375e81a4fb5d935a0262900bc998

Tx prefix hash: 0d195bd3558e78543c868cbe751dc91cb683ebed7f75bd41287f4413336c6f1e
Tx public key: 1dbdc56ec0a49a2c2eb4493041583ac584e73701bf9ad9fcf5c5a96dc5e625ad
Timestamp: 1736226553 Timestamp [UCT]: 2025-01-07 05:09:13 Age [y:d:h:m:s]: 00:306:14:31:40
Block: 1191947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216636 RingCT/type: yes/0
Extra: 011dbdc56ec0a49a2c2eb4493041583ac584e73701bf9ad9fcf5c5a96dc5e625ad02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 415ef65e77a0ce29d6f20c629edb26062bb25dfc33873b8b0f3d55ae6421ef41 0.600000000000 1678492 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": 1191957, "vin": [ { "gen": { "height": 1191947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "415ef65e77a0ce29d6f20c629edb26062bb25dfc33873b8b0f3d55ae6421ef41" } } ], "extra": [ 1, 29, 189, 197, 110, 192, 164, 154, 44, 46, 180, 73, 48, 65, 88, 58, 197, 132, 231, 55, 1, 191, 154, 217, 252, 245, 197, 169, 109, 197, 230, 37, 173, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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