Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d81951d45f0eb327e85d75fac3d540a1748b8e3a016ea12bf23b5d05582666db

Tx prefix hash: 83419e222157465f53444d2454475d68c1bdbc683193dc973b4f6d50618c2232
Tx public key: 3a7ec3620f9bb99a07703e6588675b9d9079d9458dfc007e88ae0d3122e7f1d1
Timestamp: 1705544879 Timestamp [UCT]: 2024-01-18 02:27:59 Age [y:d:h:m:s]: 01:297:01:38:07
Block: 937686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471146 RingCT/type: yes/0
Extra: 013a7ec3620f9bb99a07703e6588675b9d9079d9458dfc007e88ae0d3122e7f1d102110000000182025268000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ffdb258f182a9b21a0252455d98ed0249635179f5e4b2f0379cc7162ba0e18a 0.600000000000 1395748 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": 937696, "vin": [ { "gen": { "height": 937686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ffdb258f182a9b21a0252455d98ed0249635179f5e4b2f0379cc7162ba0e18a" } } ], "extra": [ 1, 58, 126, 195, 98, 15, 155, 185, 154, 7, 112, 62, 101, 136, 103, 91, 157, 144, 121, 217, 69, 141, 252, 0, 126, 136, 174, 13, 49, 34, 231, 241, 209, 2, 17, 0, 0, 0, 1, 130, 2, 82, 104, 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