Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45f05d65eb341916b4f75bc368c0a25fc5fd24f6dcb0f86a56de4b0257f2cc05

Tx prefix hash: 3f8b73cf337dee5b5c641d21e4050510c69ed3128519c6cf864d66270550326b
Tx public key: c2a3f284ecfd5aee30a0e92a1408809419a20ac6b99bf9dbea9b451e530504c3
Timestamp: 1703704637 Timestamp [UCT]: 2023-12-27 19:17:17 Age [y:d:h:m:s]: 01:103:08:39:04
Block: 922464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334977 RingCT/type: yes/0
Extra: 01c2a3f284ecfd5aee30a0e92a1408809419a20ac6b99bf9dbea9b451e530504c302110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21800f0b10c1ad8e3bf7c7941d11a4902fcfb55d5a6445c6a0f6f1b49b2d4fcd 0.600000000000 1380162 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": 922474, "vin": [ { "gen": { "height": 922464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21800f0b10c1ad8e3bf7c7941d11a4902fcfb55d5a6445c6a0f6f1b49b2d4fcd" } } ], "extra": [ 1, 194, 163, 242, 132, 236, 253, 90, 238, 48, 160, 233, 42, 20, 8, 128, 148, 25, 162, 10, 198, 185, 155, 249, 219, 234, 155, 69, 30, 83, 5, 4, 195, 2, 17, 0, 0, 0, 15, 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