Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e03b9d9919e85d8b027cab7b419df3cf37c3a0550c280f55abd41dca638d4f52

Tx prefix hash: 9441a2ba744aa056621c0d3234bd73064db5860cd2066ae0bf562fe27c9aa827
Tx public key: 43da20d6d178e404f0918354d5f2b6ace2d87f7c7a83b9f222b08ab46b8b8389
Timestamp: 1726552720 Timestamp [UCT]: 2024-09-17 05:58:40 Age [y:d:h:m:s]: 00:068:07:42:51
Block: 1111873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48849 RingCT/type: yes/0
Extra: 0143da20d6d178e404f0918354d5f2b6ace2d87f7c7a83b9f222b08ab46b8b838902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 363e15c5afb9bc4a086c0a74a917a95f1ce197b7b58958edfb708bde973bd1e4 0.600000000000 1590988 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": 1111883, "vin": [ { "gen": { "height": 1111873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "363e15c5afb9bc4a086c0a74a917a95f1ce197b7b58958edfb708bde973bd1e4" } } ], "extra": [ 1, 67, 218, 32, 214, 209, 120, 228, 4, 240, 145, 131, 84, 213, 242, 182, 172, 226, 216, 127, 124, 122, 131, 185, 242, 34, 176, 138, 180, 107, 139, 131, 137, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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