Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d73fa530a4ffcf97a5388c3c404e9d5c004ccc2d72652de2643c37f9ab291ca

Tx prefix hash: 608c0afa5423f329031be189519e93c0c97ef8d89120795d7b10f60bd1709166
Tx public key: f26b6c4a4679227259e46a2a970f498b8e1c80045952584f059008d49f63dd10
Timestamp: 1700403847 Timestamp [UCT]: 2023-11-19 14:24:07 Age [y:d:h:m:s]: 01:148:22:55:24
Block: 895098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367638 RingCT/type: yes/0
Extra: 01f26b6c4a4679227259e46a2a970f498b8e1c80045952584f059008d49f63dd10021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.664001016000 dcy

stealth address amount amount idx
00: 1e2fc12bf20c920624fbeb1dcb296261be0bf9ed342c202f6d748e1fc6909403 0.664001016000 1351321 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": 895108, "vin": [ { "gen": { "height": 895098 } } ], "vout": [ { "amount": 664001016, "target": { "key": "1e2fc12bf20c920624fbeb1dcb296261be0bf9ed342c202f6d748e1fc6909403" } } ], "extra": [ 1, 242, 107, 108, 74, 70, 121, 34, 114, 89, 228, 106, 42, 151, 15, 73, 139, 142, 28, 128, 4, 89, 82, 88, 79, 5, 144, 8, 212, 159, 99, 221, 16, 2, 17, 0, 0, 0, 8, 230, 210, 127, 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