Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451ea86029a60ed4c632dad9708aaf90e9a393e81990e6675ce14a9588ba60eb

Tx prefix hash: ed1e4a806d06608d52fb676d18a84078c57400dac0a5696d4fb00d674addc807
Tx public key: 2aa98feadb34a70ffeb1d4ca3cbd709d60f429ef32278b03f51c5c444ef7e700
Timestamp: 1734588219 Timestamp [UCT]: 2024-12-19 06:03:39 Age [y:d:h:m:s]: 00:112:19:52:43
Block: 1178411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80404 RingCT/type: yes/0
Extra: 012aa98feadb34a70ffeb1d4ca3cbd709d60f429ef32278b03f51c5c444ef7e700021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f14fc4f0fb15f8e0d7c9ef00246e20d3bba6d59b8eb466f4b19fd150b276f900 0.600000000000 1664798 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": 1178421, "vin": [ { "gen": { "height": 1178411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f14fc4f0fb15f8e0d7c9ef00246e20d3bba6d59b8eb466f4b19fd150b276f900" } } ], "extra": [ 1, 42, 169, 143, 234, 219, 52, 167, 15, 254, 177, 212, 202, 60, 189, 112, 157, 96, 244, 41, 239, 50, 39, 139, 3, 245, 28, 92, 68, 78, 247, 231, 0, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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