Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb310eec08ded72b86eb95d987fd83ef4b4535fc8ccb4529e8479144ea8abe15

Tx prefix hash: 84a08826ff01bfddb40d00bc3f2d22cf4c0b35f49b807116dbfa280bf2cb5b0e
Tx public key: 114929417fc30be8692365a1d2d9aa42776befd368d3ca1b819d1d02b4faab46
Timestamp: 1763935798 Timestamp [UCT]: 2025-11-23 22:09:58 Age [y:d:h:m:s]: 00:042:15:56:18
Block: 1418682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30545 RingCT/type: yes/0
Extra: 01114929417fc30be8692365a1d2d9aa42776befd368d3ca1b819d1d02b4faab46021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fc30dcdf5329f6bdd7df591582e47a17c99c716f1f4b6a758597455ae34f8e7 0.600000000000 1907215 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": 1418692, "vin": [ { "gen": { "height": 1418682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fc30dcdf5329f6bdd7df591582e47a17c99c716f1f4b6a758597455ae34f8e7" } } ], "extra": [ 1, 17, 73, 41, 65, 127, 195, 11, 232, 105, 35, 101, 161, 210, 217, 170, 66, 119, 107, 239, 211, 104, 211, 202, 27, 129, 157, 29, 2, 180, 250, 171, 70, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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