Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c3e7d898ba37d63338756e9d4117c61eea2a0ef8ab45c8bed001684b704dccb

Tx prefix hash: c9d75e386a9871707044c0e7bc9446a701bd390257505e373e92ad5572ab3001
Tx public key: 82c2083ae9eb81d7f5a58b08ef4158dc86f9dfe144d9e0f6fe5c6408839a744e
Timestamp: 1733271698 Timestamp [UCT]: 2024-12-04 00:21:38 Age [y:d:h:m:s]: 00:143:14:08:01
Block: 1167487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102443 RingCT/type: yes/0
Extra: 0182c2083ae9eb81d7f5a58b08ef4158dc86f9dfe144d9e0f6fe5c6408839a744e0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9681d0b95d5eb418b3e65d043e4d622fd3e1e68bd3425da34d53445f4111a08 0.600000000000 1653184 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": 1167497, "vin": [ { "gen": { "height": 1167487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9681d0b95d5eb418b3e65d043e4d622fd3e1e68bd3425da34d53445f4111a08" } } ], "extra": [ 1, 130, 194, 8, 58, 233, 235, 129, 215, 245, 165, 139, 8, 239, 65, 88, 220, 134, 249, 223, 225, 68, 217, 224, 246, 254, 92, 100, 8, 131, 154, 116, 78, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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