Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8506f45f07bc2f6a6870b788bda4383ef8bb15189a4cce5ed04c54672cfa64fe

Tx prefix hash: 526046f91dbaadee754d4f47a49501ac597f5bad018198ae7ed12f5e8c09f312
Tx public key: 9939aaadd83c1e032b532a45c9b405c7d2763d6c6dac71f1aa4c4291434ca67f
Timestamp: 1733263105 Timestamp [UCT]: 2024-12-03 21:58:25 Age [y:d:h:m:s]: 00:103:06:56:16
Block: 1167409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73630 RingCT/type: yes/0
Extra: 019939aaadd83c1e032b532a45c9b405c7d2763d6c6dac71f1aa4c4291434ca67f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c46d90cbe120b3df32527e90e3314115d79eae51bcb3a46103163147857e3cca 0.600000000000 1653104 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": 1167419, "vin": [ { "gen": { "height": 1167409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c46d90cbe120b3df32527e90e3314115d79eae51bcb3a46103163147857e3cca" } } ], "extra": [ 1, 153, 57, 170, 173, 216, 60, 30, 3, 43, 83, 42, 69, 201, 180, 5, 199, 210, 118, 61, 108, 109, 172, 113, 241, 170, 76, 66, 145, 67, 76, 166, 127, 2, 17, 0, 0, 0, 3, 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