Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a18a1a3c3f7056ee416543601956eabda70f906c7caf601bf4a861ec38f20fef

Tx prefix hash: 665d0346a44578ca8befe6ba3c887e5f481af89813ae9ef31e37742b769def90
Tx public key: 984de467fba22ccc52f9a0d1ae1deae53ea8a83368fb32e1930263d4f481036e
Timestamp: 1725147078 Timestamp [UCT]: 2024-08-31 23:31:18 Age [y:d:h:m:s]: 00:227:06:18:05
Block: 1100224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162285 RingCT/type: yes/0
Extra: 01984de467fba22ccc52f9a0d1ae1deae53ea8a83368fb32e1930263d4f481036e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0fa4deb9f9facd3640ea8e1b34ca55bd78cf014ccf5d71bef687beec4c46800 0.600000000000 1576197 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": 1100234, "vin": [ { "gen": { "height": 1100224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0fa4deb9f9facd3640ea8e1b34ca55bd78cf014ccf5d71bef687beec4c46800" } } ], "extra": [ 1, 152, 77, 228, 103, 251, 162, 44, 204, 82, 249, 160, 209, 174, 29, 234, 229, 62, 168, 168, 51, 104, 251, 50, 225, 147, 2, 99, 212, 244, 129, 3, 110, 2, 17, 0, 0, 0, 2, 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