Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e468ccf4a1f637f5337164c34160988c0e81c923a1d1a58bd939a2b039177cc8

Tx prefix hash: c4ee871c92a01aa039c5f436f8ad213d6a42556cad9499d82813eb5615dbc5ad
Tx public key: 520b3e2a4d4b45557d234927f00e0cc4857e39f6ff9ed5235b04bcef85138c86
Timestamp: 1734328362 Timestamp [UCT]: 2024-12-16 05:52:42 Age [y:d:h:m:s]: 00:100:01:37:19
Block: 1176257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71271 RingCT/type: yes/0
Extra: 01520b3e2a4d4b45557d234927f00e0cc4857e39f6ff9ed5235b04bcef85138c860211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d8f53da5f9094fc6965d372a771a3b5b3a5ecdb92c8ebdb41f96487cbb9941c 0.600000000000 1662588 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": 1176267, "vin": [ { "gen": { "height": 1176257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d8f53da5f9094fc6965d372a771a3b5b3a5ecdb92c8ebdb41f96487cbb9941c" } } ], "extra": [ 1, 82, 11, 62, 42, 77, 75, 69, 85, 125, 35, 73, 39, 240, 14, 12, 196, 133, 126, 57, 246, 255, 158, 213, 35, 91, 4, 188, 239, 133, 19, 140, 134, 2, 17, 0, 0, 0, 4, 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