Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f5295a5bdce38f4ac883d80121778e861c2384c7b72b692642079cc5ea5d4be

Tx prefix hash: 74390fa8e14b02635c3865c13838918632632e5cbe67cd88c692d4a901addda3
Tx public key: 158246a0e1b6a9253efeaf1ec115bcc093e4b8ca7c85808c59b5d47b866ebabe
Timestamp: 1738300834 Timestamp [UCT]: 2025-01-31 05:20:34 Age [y:d:h:m:s]: 00:137:07:09:56
Block: 1208855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98100 RingCT/type: yes/0
Extra: 01158246a0e1b6a9253efeaf1ec115bcc093e4b8ca7c85808c59b5d47b866ebabe021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d69cc4b1381e4b11abd579429fce1d0a4b8f54584963cf32b3c3357d2b4f73d 0.600000000000 1695590 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": 1208865, "vin": [ { "gen": { "height": 1208855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d69cc4b1381e4b11abd579429fce1d0a4b8f54584963cf32b3c3357d2b4f73d" } } ], "extra": [ 1, 21, 130, 70, 160, 225, 182, 169, 37, 62, 254, 175, 30, 193, 21, 188, 192, 147, 228, 184, 202, 124, 133, 128, 140, 89, 181, 212, 123, 134, 110, 186, 190, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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