Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6368bd4b934ec35e5bcf8c4c8efa66d96de8aaac5123ed2a58130215e9832536

Tx prefix hash: 5da4fd0b4fe6f64ce1ae6d7d82d2c46e8796a00c75de59198c929a115e9529a3
Tx public key: f814caabba1b4eab9b80e44a17e5cb4433fa7ccad601a711a7a78a6c6fdfc951
Timestamp: 1673037247 Timestamp [UCT]: 2023-01-06 20:34:07 Age [y:d:h:m:s]: 02:101:11:05:17
Block: 669072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594199 RingCT/type: yes/0
Extra: 01f814caabba1b4eab9b80e44a17e5cb4433fa7ccad601a711a7a78a6c6fdfc951021100000002faf35c9c000000000000000000

1 output(s) for total of 3.724660366000 dcy

stealth address amount amount idx
00: 89a15a9970f593667d081a3f35312d73deb7ad183fc46857af45f121606aee83 3.724660366000 1110359 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": 669082, "vin": [ { "gen": { "height": 669072 } } ], "vout": [ { "amount": 3724660366, "target": { "key": "89a15a9970f593667d081a3f35312d73deb7ad183fc46857af45f121606aee83" } } ], "extra": [ 1, 248, 20, 202, 171, 186, 27, 78, 171, 155, 128, 228, 74, 23, 229, 203, 68, 51, 250, 124, 202, 214, 1, 167, 17, 167, 167, 138, 108, 111, 223, 201, 81, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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