Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b2a3f1d6a4ecfa8495521c782b151ff68b7d27b5082441509ff1d774fd28d1b

Tx prefix hash: ca67e5fd72a299333406be6a0774f2f1e1e545d8fda4dabba6e758d49010541b
Tx public key: 651e003b1da0c45b2a6c228dff4983961cb98d76834a1988e238d4b059dcfcb1
Timestamp: 1718123351 Timestamp [UCT]: 2024-06-11 16:29:11 Age [y:d:h:m:s]: 01:006:00:03:43
Block: 1042007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265059 RingCT/type: yes/0
Extra: 01651e003b1da0c45b2a6c228dff4983961cb98d76834a1988e238d4b059dcfcb102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13d3bf0528d227ead1866da9a0d837294a3734cfcf3738c9922e3056cc432042 0.600000000000 1510818 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": 1042017, "vin": [ { "gen": { "height": 1042007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13d3bf0528d227ead1866da9a0d837294a3734cfcf3738c9922e3056cc432042" } } ], "extra": [ 1, 101, 30, 0, 59, 29, 160, 196, 91, 42, 108, 34, 141, 255, 73, 131, 150, 28, 185, 141, 118, 131, 74, 25, 136, 226, 56, 212, 176, 89, 220, 252, 177, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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