Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9158fafc6c6c344e22848162459fb3101be0da1553d76e10c2c6b63762bf0f33

Tx prefix hash: cd645990a9b3b4b91ec11aed1012b45d014236563949a3526571f56b2b08981c
Tx public key: 607fce4e4ee8b2ae67e7afe229ae7b4144076d1c253e5b6f0cdc5fa0baa70796
Timestamp: 1736670449 Timestamp [UCT]: 2025-01-12 08:27:29 Age [y:d:h:m:s]: 00:081:14:54:36
Block: 1195621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58108 RingCT/type: yes/0
Extra: 01607fce4e4ee8b2ae67e7afe229ae7b4144076d1c253e5b6f0cdc5fa0baa707960211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a62704382fd67a0a481a1b66a7323244ed7f0609b07a1cf6994e41de9926f805 0.600000000000 1682212 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": 1195631, "vin": [ { "gen": { "height": 1195621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a62704382fd67a0a481a1b66a7323244ed7f0609b07a1cf6994e41de9926f805" } } ], "extra": [ 1, 96, 127, 206, 78, 78, 232, 178, 174, 103, 231, 175, 226, 41, 174, 123, 65, 68, 7, 109, 28, 37, 62, 91, 111, 12, 220, 95, 160, 186, 167, 7, 150, 2, 17, 0, 0, 0, 2, 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