Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44329bd8ba49b69555b01c2f2aab366d4baafed522dac946aee201297d0446d2

Tx prefix hash: d21658224287f25c1c115466eddc2af8ae0a677cc442c908ea3d692792610b0a
Tx public key: d37300c2f7eabe9059da7d3e19ba06953d809f6d4836cd7f7f79f299c3325b9f
Timestamp: 1747470889 Timestamp [UCT]: 2025-05-17 08:34:49 Age [y:d:h:m:s]: 00:188:12:42:25
Block: 1284769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132445 RingCT/type: yes/0
Extra: 01d37300c2f7eabe9059da7d3e19ba06953d809f6d4836cd7f7f79f299c3325b9f0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74331385f10ba3f8720f904db7317da61d35e3eb189d6a5ff14a51875ae578b6 0.600000000000 1772232 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": 1284779, "vin": [ { "gen": { "height": 1284769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74331385f10ba3f8720f904db7317da61d35e3eb189d6a5ff14a51875ae578b6" } } ], "extra": [ 1, 211, 115, 0, 194, 247, 234, 190, 144, 89, 218, 125, 62, 25, 186, 6, 149, 61, 128, 159, 109, 72, 54, 205, 127, 127, 121, 242, 153, 195, 50, 91, 159, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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