Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b95b74758166fc0cf8827bede295109e157e735b60ef336f95913bce2649a84

Tx prefix hash: 0fcceee3c2d7cfe2aad1258c468389e3df94dbfffc8c56bb1b196dcc5dea8eaa
Tx public key: cd7f8d5dab534366f6ef4721b45d9b0172fc6f8df48d0a67c930dff3f3455ea2
Timestamp: 1705297451 Timestamp [UCT]: 2024-01-15 05:44:11 Age [y:d:h:m:s]: 01:086:17:18:18
Block: 935637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323089 RingCT/type: yes/0
Extra: 01cd7f8d5dab534366f6ef4721b45d9b0172fc6f8df48d0a67c930dff3f3455ea20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77c7c60eaa6cd0679a20e670b0ee7174bdeb979ffcc97304781631c3fa8459c4 0.600000000000 1393653 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": 935647, "vin": [ { "gen": { "height": 935637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77c7c60eaa6cd0679a20e670b0ee7174bdeb979ffcc97304781631c3fa8459c4" } } ], "extra": [ 1, 205, 127, 141, 93, 171, 83, 67, 102, 246, 239, 71, 33, 180, 93, 155, 1, 114, 252, 111, 141, 244, 141, 10, 103, 201, 48, 223, 243, 243, 69, 94, 162, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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