Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e04c5f27de9477d39706ed7032ec5159a2287b881acce8884d0f88c1cf35bb1b

Tx prefix hash: 17a0b1df8cdaef6296ced719ee390c722bf2b60502eec4d3509ff8f0fb162c52
Tx public key: 33289045b4b92e4052b858c1e373a306f472afbce3163ca7ab283e8de04a268a
Timestamp: 1725666746 Timestamp [UCT]: 2024-09-06 23:52:26 Age [y:d:h:m:s]: 00:145:21:59:45
Block: 1104542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104093 RingCT/type: yes/0
Extra: 0133289045b4b92e4052b858c1e373a306f472afbce3163ca7ab283e8de04a268a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa26fb6a5e3bac18032f13f618c585447f089f7f84e830aed0b454c9f6bcbb2 0.600000000000 1581719 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": 1104552, "vin": [ { "gen": { "height": 1104542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa26fb6a5e3bac18032f13f618c585447f089f7f84e830aed0b454c9f6bcbb2" } } ], "extra": [ 1, 51, 40, 144, 69, 180, 185, 46, 64, 82, 184, 88, 193, 227, 115, 163, 6, 244, 114, 175, 188, 227, 22, 60, 167, 171, 40, 62, 141, 224, 74, 38, 138, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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