Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0dd1992831280bf246b28f9f7c92835a64b23c8a08723b6d2e31917a2797692

Tx prefix hash: 634508c72b527747fcd3458e7f7de2a9535b77528d22dee17ec1b25aaa4570f8
Tx public key: b11fbe6e2ee8d76049bbe3ed1c09c24652d2c3c2d940456483a35f97b20d731c
Timestamp: 1730115356 Timestamp [UCT]: 2024-10-28 11:35:56 Age [y:d:h:m:s]: 00:158:05:24:24
Block: 1141346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112911 RingCT/type: yes/0
Extra: 01b11fbe6e2ee8d76049bbe3ed1c09c24652d2c3c2d940456483a35f97b20d731c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cce397fffebf73ebd71cb82c2252c140fd8f85e067bba3881ebc8355d389c194 0.600000000000 1625153 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": 1141356, "vin": [ { "gen": { "height": 1141346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cce397fffebf73ebd71cb82c2252c140fd8f85e067bba3881ebc8355d389c194" } } ], "extra": [ 1, 177, 31, 190, 110, 46, 232, 215, 96, 73, 187, 227, 237, 28, 9, 194, 70, 82, 210, 195, 194, 217, 64, 69, 100, 131, 163, 95, 151, 178, 13, 115, 28, 2, 17, 0, 0, 0, 6, 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