Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6d9816d0451e42e1b2aee4dff53a36220967d4584915f60d145c0968f97c2e8

Tx prefix hash: f6cfe0b524be96e6b6bb23bf5b16907b7868fc2e8dccd5f8ec7f7da8b66f5528
Tx public key: 7b4691ae516a67133b0fb68a50872cb8cf91b60459fba8eefd3c80d080e29f20
Timestamp: 1684941269 Timestamp [UCT]: 2023-05-24 15:14:29 Age [y:d:h:m:s]: 01:324:05:38:13
Block: 767154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492940 RingCT/type: yes/0
Extra: 017b4691ae516a67133b0fb68a50872cb8cf91b60459fba8eefd3c80d080e29f2002110000000275e3f0e9000000000000000000

1 output(s) for total of 1.762383894000 dcy

stealth address amount amount idx
00: b67c99287b4318ac0a5a40dc325e3131a5d192e33ccad9899a3e7674c549e778 1.762383894000 1216259 of 0

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": 767164, "vin": [ { "gen": { "height": 767154 } } ], "vout": [ { "amount": 1762383894, "target": { "key": "b67c99287b4318ac0a5a40dc325e3131a5d192e33ccad9899a3e7674c549e778" } } ], "extra": [ 1, 123, 70, 145, 174, 81, 106, 103, 19, 59, 15, 182, 138, 80, 135, 44, 184, 207, 145, 182, 4, 89, 251, 168, 238, 253, 60, 128, 208, 128, 226, 159, 32, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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