Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f433d96746040d7e3ba237287df4e1afd2bb14808979ed2b0545e334173eaf11

Tx prefix hash: 14bfe5ffa979a3325319d85522def431cb18b626aa0ed5b80999444e4f5a8c67
Tx public key: fb9d97ed6e35d04ef1e82a31f3e0cc15a103a2d464aee01c891583bcd57ba1c5
Timestamp: 1723139581 Timestamp [UCT]: 2024-08-08 17:53:01 Age [y:d:h:m:s]: 00:311:11:58:00
Block: 1083576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222470 RingCT/type: yes/0
Extra: 01fb9d97ed6e35d04ef1e82a31f3e0cc15a103a2d464aee01c891583bcd57ba1c502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: def9e34e939e0819999db983e91bb2d922e08e38f291e3df179912f9835bd60b 0.600000000000 1557549 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": 1083586, "vin": [ { "gen": { "height": 1083576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "def9e34e939e0819999db983e91bb2d922e08e38f291e3df179912f9835bd60b" } } ], "extra": [ 1, 251, 157, 151, 237, 110, 53, 208, 78, 241, 232, 42, 49, 243, 224, 204, 21, 161, 3, 162, 212, 100, 174, 224, 28, 137, 21, 131, 188, 213, 123, 161, 197, 2, 17, 0, 0, 0, 4, 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