Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19b99f474a16bb988c167c604e3bb7f2aaf74b3858a0197d5de2b4f0c8e65db8

Tx prefix hash: fd0bb15a8dd33c9f849f8cf9afe5fff3b5be60005c7134ebaacbe21ed325d0e3
Tx public key: 205342f8c0f961eb6c885bcc7c38db4f2838b7f42a54bb9f493101daa4f6cf8d
Timestamp: 1725566569 Timestamp [UCT]: 2024-09-05 20:02:49 Age [y:d:h:m:s]: 00:221:13:11:20
Block: 1103706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158189 RingCT/type: yes/0
Extra: 01205342f8c0f961eb6c885bcc7c38db4f2838b7f42a54bb9f493101daa4f6cf8d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6cab089eaaf7d7922ae7c7332d45d6d8251246edb4b076d7d2fa7999787827f 0.600000000000 1580639 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": 1103716, "vin": [ { "gen": { "height": 1103706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6cab089eaaf7d7922ae7c7332d45d6d8251246edb4b076d7d2fa7999787827f" } } ], "extra": [ 1, 32, 83, 66, 248, 192, 249, 97, 235, 108, 136, 91, 204, 124, 56, 219, 79, 40, 56, 183, 244, 42, 84, 187, 159, 73, 49, 1, 218, 164, 246, 207, 141, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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