Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92e29a880a4805f81364b991d893bc624c64c7795aeabaf730822d17a1ea2d7b

Tx prefix hash: 3d73815ec7df27a15390c0310dd8f591e7475089e3a621aac77922215457d07b
Tx public key: 1542bf6ce55de3794abcd0d3af2bc000b86a3f278df8e94db7b4e06f32c9160a
Timestamp: 1721467375 Timestamp [UCT]: 2024-07-20 09:22:55 Age [y:d:h:m:s]: 00:298:10:26:13
Block: 1069719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213244 RingCT/type: yes/0
Extra: 011542bf6ce55de3794abcd0d3af2bc000b86a3f278df8e94db7b4e06f32c9160a02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 287d8af40d7ccd2e710febefdfafe5f397fa1503aa382c95a0628c9225598fd8 0.600000000000 1541260 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": 1069729, "vin": [ { "gen": { "height": 1069719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "287d8af40d7ccd2e710febefdfafe5f397fa1503aa382c95a0628c9225598fd8" } } ], "extra": [ 1, 21, 66, 191, 108, 229, 93, 227, 121, 74, 188, 208, 211, 175, 43, 192, 0, 184, 106, 63, 39, 141, 248, 233, 77, 183, 180, 224, 111, 50, 201, 22, 10, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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