Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ff85af65b6bacca82ba1da7515cba8a3e38dc82321a038c5d0a46283f02e43

Tx prefix hash: 2bf7b78956fcb4cfb59d2b75b70d36d971f79342730d68f8b80f3c41c1447c5e
Tx public key: 7926b2326c71a6dfc8418c52dc238a47300e3deebbb2761cc384f74f3b652f75
Timestamp: 1721862934 Timestamp [UCT]: 2024-07-24 23:15:34 Age [y:d:h:m:s]: 00:327:15:06:13
Block: 1072997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234010 RingCT/type: yes/0
Extra: 017926b2326c71a6dfc8418c52dc238a47300e3deebbb2761cc384f74f3b652f75021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1744d54629a2921d7d58a35019e1658c367be5afe339fd8bfcca31aa0c8e55d4 0.600000000000 1545496 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": 1073007, "vin": [ { "gen": { "height": 1072997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1744d54629a2921d7d58a35019e1658c367be5afe339fd8bfcca31aa0c8e55d4" } } ], "extra": [ 1, 121, 38, 178, 50, 108, 113, 166, 223, 200, 65, 140, 82, 220, 35, 138, 71, 48, 14, 61, 238, 187, 178, 118, 28, 195, 132, 247, 79, 59, 101, 47, 117, 2, 17, 0, 0, 0, 3, 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