Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34351d209b951017d813f2eece8b40ab0132bc3968f3bb4eb63d40ea847a2840

Tx prefix hash: 2a465eb047efa53a90e8a236042ebaa2e2da1c41e32849efb8d1cbf2628ceffa
Tx public key: befae284e239a7d8d0abaa01d942b4583ce447082043dde8dc3a534084727e15
Timestamp: 1702688079 Timestamp [UCT]: 2023-12-16 00:54:39 Age [y:d:h:m:s]: 01:183:07:38:12
Block: 914029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392087 RingCT/type: yes/0
Extra: 01befae284e239a7d8d0abaa01d942b4583ce447082043dde8dc3a534084727e1502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e92807926953d8116f7bc56d60d906f5670d4d18f2db7bd7e59232ed01e13628 0.600000000000 1371311 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": 914039, "vin": [ { "gen": { "height": 914029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e92807926953d8116f7bc56d60d906f5670d4d18f2db7bd7e59232ed01e13628" } } ], "extra": [ 1, 190, 250, 226, 132, 226, 57, 167, 216, 208, 171, 170, 1, 217, 66, 180, 88, 60, 228, 71, 8, 32, 67, 221, 232, 220, 58, 83, 64, 132, 114, 126, 21, 2, 17, 0, 0, 0, 2, 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