Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c8ce885d118ef5fee85949b6a150e815e7a8c79fa53bce28c3dd6827d05039

Tx prefix hash: 387eb9db6192840f38e5077c1d015cb0eb48f4c568a12cefeba83731b7eb6381
Tx public key: f79dbb46508d4222ab32b2c0a03052fd2a36eab7bef11c5fd422accef6c1d515
Timestamp: 1736698197 Timestamp [UCT]: 2025-01-12 16:09:57 Age [y:d:h:m:s]: 00:079:00:32:59
Block: 1195852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56242 RingCT/type: yes/0
Extra: 01f79dbb46508d4222ab32b2c0a03052fd2a36eab7bef11c5fd422accef6c1d5150211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fc43f16868a12c5341637567900d5133e3e589dc9f4f69bb5c85f43ee2ee088 0.600000000000 1682445 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": 1195862, "vin": [ { "gen": { "height": 1195852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fc43f16868a12c5341637567900d5133e3e589dc9f4f69bb5c85f43ee2ee088" } } ], "extra": [ 1, 247, 157, 187, 70, 80, 141, 66, 34, 171, 50, 178, 192, 160, 48, 82, 253, 42, 54, 234, 183, 190, 241, 28, 95, 212, 34, 172, 206, 246, 193, 213, 21, 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