Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9d11f621fca1aba1da7d20ce36caf3a802166e8186d5d98cfa524583f8f566d

Tx prefix hash: 00f84ce55567162878e932df2cdbc336f7f0e1e0b19812f1769afe5c7e2abd20
Tx public key: c078cb22f5bd36344d543aa7757fb23b65c48a6c95eaf92ee83a646f91834779
Timestamp: 1713368981 Timestamp [UCT]: 2024-04-17 15:49:41 Age [y:d:h:m:s]: 01:041:06:11:39
Block: 1002572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290469 RingCT/type: yes/0
Extra: 01c078cb22f5bd36344d543aa7757fb23b65c48a6c95eaf92ee83a646f9183477902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b0300b30329db6402d0c11d9b8f9b130d3d895e4579c99c51a9c3968db4a859 0.600000000000 1463090 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": 1002582, "vin": [ { "gen": { "height": 1002572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b0300b30329db6402d0c11d9b8f9b130d3d895e4579c99c51a9c3968db4a859" } } ], "extra": [ 1, 192, 120, 203, 34, 245, 189, 54, 52, 77, 84, 58, 167, 117, 127, 178, 59, 101, 196, 138, 108, 149, 234, 249, 46, 232, 58, 100, 111, 145, 131, 71, 121, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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