Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 064c1fe7941ca8235befeca7bb8f8ef868dc0ed195fc2b9917ae263d9019ad9b

Tx prefix hash: 0e9913bcc52d7382b3765b0ee1fe57f6687ba03df2b50ac505a3cd5c42c4e05b
Tx public key: 1bb3b303b790bbf1b4b9804ab1ab12fb1965009abc0c7b6339007a8eea65a58c
Timestamp: 1749236157 Timestamp [UCT]: 2025-06-06 18:55:57 Age [y:d:h:m:s]: 00:166:13:05:32
Block: 1299388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116717 RingCT/type: yes/0
Extra: 011bb3b303b790bbf1b4b9804ab1ab12fb1965009abc0c7b6339007a8eea65a58c021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41e1478b6f9044524afd84ed94d653385e20ac3fbca6e5856843864d174654e2 0.600000000000 1786925 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": 1299398, "vin": [ { "gen": { "height": 1299388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41e1478b6f9044524afd84ed94d653385e20ac3fbca6e5856843864d174654e2" } } ], "extra": [ 1, 27, 179, 179, 3, 183, 144, 187, 241, 180, 185, 128, 74, 177, 171, 18, 251, 25, 101, 0, 154, 188, 12, 123, 99, 57, 0, 122, 142, 234, 101, 165, 140, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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