Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88ff0f7b0c4edbb64f7dd30fd9a337111f65f101f3f40f07e5c66dfa7fdb406a

Tx prefix hash: 8423f219895aecd2df9c84ad207e69ca66ff68c4c879acec0b6ea1cd13fecc8c
Tx public key: ba194d792d71e2ec950091bc15b8d7b84575de1d128c8352c9793d4a8bafe623
Timestamp: 1731796563 Timestamp [UCT]: 2024-11-16 22:36:03 Age [y:d:h:m:s]: 00:126:08:08:54
Block: 1155250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90120 RingCT/type: yes/0
Extra: 01ba194d792d71e2ec950091bc15b8d7b84575de1d128c8352c9793d4a8bafe623021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70f1e9533efb9394fda436ea49f04c4496e04a2bd4801a56917be14d0800f805 0.600000000000 1640865 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": 1155260, "vin": [ { "gen": { "height": 1155250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70f1e9533efb9394fda436ea49f04c4496e04a2bd4801a56917be14d0800f805" } } ], "extra": [ 1, 186, 25, 77, 121, 45, 113, 226, 236, 149, 0, 145, 188, 21, 184, 215, 184, 69, 117, 222, 29, 18, 140, 131, 82, 201, 121, 61, 74, 139, 175, 230, 35, 2, 17, 0, 0, 0, 2, 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