Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f963bdc09c94eb72e32f450951c449d98786b098e2225f86f7a8e6f287c4569f

Tx prefix hash: 37c3269d0a2ffa3490f4d69f01f6cc6f98d3f156027ca4a7ba225b0ce6126e03
Tx public key: 21bb788f3e0fe59056853d5a13cb78ab762c1107e9ad857ab8d5457f4f600978
Timestamp: 1736360820 Timestamp [UCT]: 2025-01-08 18:27:00 Age [y:d:h:m:s]: 00:087:22:37:31
Block: 1193061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62617 RingCT/type: yes/0
Extra: 0121bb788f3e0fe59056853d5a13cb78ab762c1107e9ad857ab8d5457f4f60097802110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f99e36d357609e0e37ab1a537876d70e7aec98b045712d7a093ae83f8c2bf583 0.600000000000 1679618 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": 1193071, "vin": [ { "gen": { "height": 1193061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f99e36d357609e0e37ab1a537876d70e7aec98b045712d7a093ae83f8c2bf583" } } ], "extra": [ 1, 33, 187, 120, 143, 62, 15, 229, 144, 86, 133, 61, 90, 19, 203, 120, 171, 118, 44, 17, 7, 233, 173, 133, 122, 184, 213, 69, 127, 79, 96, 9, 120, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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