Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6e8e1d02a14754c8d7808bca6838eb8c73dd137e984aac8fc362dab92ea97b

Tx prefix hash: 7bbf1ee6111216916a6ca9e1e5a08a4ad6379524ce36d36ca545cded7192268f
Tx public key: 0dbc6fef9063416318118a4fa2cf49a45bcd25118d6d4d282b205a9df27b6c5d
Timestamp: 1722736002 Timestamp [UCT]: 2024-08-04 01:46:42 Age [y:d:h:m:s]: 00:249:17:11:09
Block: 1080241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178365 RingCT/type: yes/0
Extra: 010dbc6fef9063416318118a4fa2cf49a45bcd25118d6d4d282b205a9df27b6c5d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae6299530a0dbfbce4688e5062107ff49a305434e3bcc424a7bdfc0cba58cf8d 0.600000000000 1553522 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": 1080251, "vin": [ { "gen": { "height": 1080241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae6299530a0dbfbce4688e5062107ff49a305434e3bcc424a7bdfc0cba58cf8d" } } ], "extra": [ 1, 13, 188, 111, 239, 144, 99, 65, 99, 24, 17, 138, 79, 162, 207, 73, 164, 91, 205, 37, 17, 141, 109, 77, 40, 43, 32, 90, 157, 242, 123, 108, 93, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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