Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a836ea199fd91cba2c0a7cd55cc58911167e4de261a40cfa5f3b5dba2ea81f

Tx prefix hash: b199e0b66b4f2090ad4e45793a08359d29ffc88ba79f469ab4fd5a27af149c75
Tx public key: 110f1f5607a7a18ebaafec0f7285b3ebdfbeccbab34e2c6aa62077af6281466a
Timestamp: 1717588473 Timestamp [UCT]: 2024-06-05 11:54:33 Age [y:d:h:m:s]: 00:285:11:53:34
Block: 1037568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204034 RingCT/type: yes/0
Extra: 01110f1f5607a7a18ebaafec0f7285b3ebdfbeccbab34e2c6aa62077af6281466a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f066e074d6488c8460c88c308f7ce1f0070f25641be75e444a8b1adca0491bf 0.600000000000 1506113 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": 1037578, "vin": [ { "gen": { "height": 1037568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f066e074d6488c8460c88c308f7ce1f0070f25641be75e444a8b1adca0491bf" } } ], "extra": [ 1, 17, 15, 31, 86, 7, 167, 161, 142, 186, 175, 236, 15, 114, 133, 179, 235, 223, 190, 204, 186, 179, 78, 44, 106, 166, 32, 119, 175, 98, 129, 70, 106, 2, 17, 0, 0, 0, 3, 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