Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d093e236fb91a30937e4ef7f6d51bac90408248cfeaad7f73873f5b3a6ecbcc4

Tx prefix hash: d2638571b024225aa45f985449aa20f18ffbf66db72d35f419ac51b7ca5dac95
Tx public key: 95e7289be9c43f854a48bbbb5505ca7592ca1d61b61986a244aeee4a7f10a5ca
Timestamp: 1737124953 Timestamp [UCT]: 2025-01-17 14:42:33 Age [y:d:h:m:s]: 00:152:06:13:53
Block: 1199375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108514 RingCT/type: yes/0
Extra: 0195e7289be9c43f854a48bbbb5505ca7592ca1d61b61986a244aeee4a7f10a5ca0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 482a87c3bf8de9739285328e444b4805863f5ae93c5d8a11224f4bd1d37fd6ff 0.600000000000 1686006 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": 1199385, "vin": [ { "gen": { "height": 1199375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "482a87c3bf8de9739285328e444b4805863f5ae93c5d8a11224f4bd1d37fd6ff" } } ], "extra": [ 1, 149, 231, 40, 155, 233, 196, 63, 133, 74, 72, 187, 187, 85, 5, 202, 117, 146, 202, 29, 97, 182, 25, 134, 162, 68, 174, 238, 74, 127, 16, 165, 202, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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