Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8958595acbd3b679f0a03542585a894988549a6c18f514ffcdf60c2650d3bb1b

Tx prefix hash: 6c970a9f574e7f25ff59fbe750bd59682c422de053741cdadcc17a2c66196535
Tx public key: 52a2d9365aa1f4e0dbede9ae453a26d2c94ea4e15e4316339e54b0c8dce05fe4
Timestamp: 1696656111 Timestamp [UCT]: 2023-10-07 05:21:51 Age [y:d:h:m:s]: 01:096:00:16:57
Block: 864223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329881 RingCT/type: yes/0
Extra: 0152a2d9365aa1f4e0dbede9ae453a26d2c94ea4e15e4316339e54b0c8dce05fe402110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.840369885000 dcy

stealth address amount amount idx
00: 1f6597ee1c2b0f403c3e34867f09e9b6e4819d9b014611716fa5a1a58b157114 0.840369885000 1318733 of 0

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": 864233, "vin": [ { "gen": { "height": 864223 } } ], "vout": [ { "amount": 840369885, "target": { "key": "1f6597ee1c2b0f403c3e34867f09e9b6e4819d9b014611716fa5a1a58b157114" } } ], "extra": [ 1, 82, 162, 217, 54, 90, 161, 244, 224, 219, 237, 233, 174, 69, 58, 38, 210, 201, 78, 164, 225, 94, 67, 22, 51, 158, 84, 176, 200, 220, 224, 95, 228, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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