Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dba7b19ecc362cce4ad6e8ab2c8dd7ae774819318b20be2007224cfee883c90a

Tx prefix hash: ff543e1203b25e9adf07764599947a9f86a4b962b693ed3d5ef8ebea3fb86c41
Tx public key: dd05e117c6e79e06406f2fb146a4271f6fdba0ca7aada4d9f2ea49a43da52421
Timestamp: 1723407328 Timestamp [UCT]: 2024-08-11 20:15:28 Age [y:d:h:m:s]: 00:246:15:47:14
Block: 1085798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176177 RingCT/type: yes/0
Extra: 01dd05e117c6e79e06406f2fb146a4271f6fdba0ca7aada4d9f2ea49a43da52421021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa24619cd29d03b474a9591a79316c3baea62170690ada47884501eb4f74e9a 0.600000000000 1560387 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": 1085808, "vin": [ { "gen": { "height": 1085798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa24619cd29d03b474a9591a79316c3baea62170690ada47884501eb4f74e9a" } } ], "extra": [ 1, 221, 5, 225, 23, 198, 231, 158, 6, 64, 111, 47, 177, 70, 164, 39, 31, 111, 219, 160, 202, 122, 173, 164, 217, 242, 234, 73, 164, 61, 165, 36, 33, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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