Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99d855a11ccd48ce1195851f7ae782053aaaf690a3dce5a3bb79507c8011299f

Tx prefix hash: 1a0559507622a3b1778fa08574cda3a9709dc8667416bbcc676989d804e1ffb2
Tx public key: 5135a6dbd92961f7c1f1dbed2a78a364ec0ae7fcf3d0bc2048f4e93e564ef426
Timestamp: 1736796727 Timestamp [UCT]: 2025-01-13 19:32:07 Age [y:d:h:m:s]: 00:155:15:29:12
Block: 1196664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110949 RingCT/type: yes/0
Extra: 015135a6dbd92961f7c1f1dbed2a78a364ec0ae7fcf3d0bc2048f4e93e564ef426021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69e4b96a33fb5c7121fecca0922df764715317b10ed5d62efe3b6afed83458a0 0.600000000000 1683265 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": 1196674, "vin": [ { "gen": { "height": 1196664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69e4b96a33fb5c7121fecca0922df764715317b10ed5d62efe3b6afed83458a0" } } ], "extra": [ 1, 81, 53, 166, 219, 217, 41, 97, 247, 193, 241, 219, 237, 42, 120, 163, 100, 236, 10, 231, 252, 243, 208, 188, 32, 72, 244, 233, 62, 86, 78, 244, 38, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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