Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52a5ff6e1599d5d420d36965c3184c8dc246a5b2dc495d9aee0943a07593137d

Tx prefix hash: 81e97605a93a894c51d157430935c9ba45e991ae357443c852a5509fd14fb1f4
Tx public key: 0d44f6bdf1f3f9f8613fcaa5e700ee77c8cc14151ea40d51573f83b0b2cf2f7b
Timestamp: 1727343576 Timestamp [UCT]: 2024-09-26 09:39:36 Age [y:d:h:m:s]: 00:186:10:16:57
Block: 1118436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133049 RingCT/type: yes/0
Extra: 010d44f6bdf1f3f9f8613fcaa5e700ee77c8cc14151ea40d51573f83b0b2cf2f7b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fda2a85ee52147da89c3aaee929872a655f492ea1b703c502ff0f70f7023dc12 0.600000000000 1599629 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": 1118446, "vin": [ { "gen": { "height": 1118436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fda2a85ee52147da89c3aaee929872a655f492ea1b703c502ff0f70f7023dc12" } } ], "extra": [ 1, 13, 68, 246, 189, 241, 243, 249, 248, 97, 63, 202, 165, 231, 0, 238, 119, 200, 204, 20, 21, 30, 164, 13, 81, 87, 63, 131, 176, 178, 207, 47, 123, 2, 17, 0, 0, 0, 1, 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