Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c793f3aa7a720d5077a3c294c94cf985b15cac100bbb5d9f9952d4ccecc541

Tx prefix hash: dc74d267ee8666eb5750b8552ccb4d0067ea90c505de6050873cc6dc48041b48
Tx public key: bcd1537de75a59218f601b828450ac013fb275c71c4c7aa8e4ac57d700452c2e
Timestamp: 1725376901 Timestamp [UCT]: 2024-09-03 15:21:41 Age [y:d:h:m:s]: 00:264:03:29:00
Block: 1102139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188664 RingCT/type: yes/0
Extra: 01bcd1537de75a59218f601b828450ac013fb275c71c4c7aa8e4ac57d700452c2e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ed2b5905a7182697ae3c8a9f44ca887ee31b55dbd0b47248234a34d4b11a8c4 0.600000000000 1578454 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": 1102149, "vin": [ { "gen": { "height": 1102139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ed2b5905a7182697ae3c8a9f44ca887ee31b55dbd0b47248234a34d4b11a8c4" } } ], "extra": [ 1, 188, 209, 83, 125, 231, 90, 89, 33, 143, 96, 27, 130, 132, 80, 172, 1, 63, 178, 117, 199, 28, 76, 122, 168, 228, 172, 87, 215, 0, 69, 44, 46, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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