Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfafa6b55b26d627820343af08209347a6ae4a009b6150f7e8592bc23c1d60ba

Tx prefix hash: f342dc1ca341aeec1f31747ee6aad2977eab5fabf623db7b87efaa6bd16be0a3
Tx public key: 154d9b1945b126d4310c1df00032f8fa6a755be9d2da80bb81f1f3d6073f71d1
Timestamp: 1743489570 Timestamp [UCT]: 2025-04-01 06:39:30 Age [y:d:h:m:s]: 00:233:01:21:59
Block: 1251800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164306 RingCT/type: yes/0
Extra: 01154d9b1945b126d4310c1df00032f8fa6a755be9d2da80bb81f1f3d6073f71d102110000000da2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a823f5d2b0ba90575f22ace1ac19c7004e7332bdbaa815ef4f857e3a2723195 0.600000000000 1738869 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": 1251810, "vin": [ { "gen": { "height": 1251800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a823f5d2b0ba90575f22ace1ac19c7004e7332bdbaa815ef4f857e3a2723195" } } ], "extra": [ 1, 21, 77, 155, 25, 69, 177, 38, 212, 49, 12, 29, 240, 0, 50, 248, 250, 106, 117, 91, 233, 210, 218, 128, 187, 129, 241, 243, 214, 7, 63, 113, 209, 2, 17, 0, 0, 0, 13, 162, 237, 1, 107, 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