Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5257505796e5c0b0cfb8f32c17097db6969b2c80247cc3f4a4963f2068fc9194

Tx prefix hash: 019028a55f9afaf3fe86c53ff0f8f7697e272e4c10f2bf1c65bec0d2b1359edf
Tx public key: f5019beb2cf55a085f72040280fcdf8395e0ca9ac3d46dbfff87229e429ba6f1
Timestamp: 1706422190 Timestamp [UCT]: 2024-01-28 06:09:50 Age [y:d:h:m:s]: 01:028:03:40:17
Block: 944963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281176 RingCT/type: yes/0
Extra: 01f5019beb2cf55a085f72040280fcdf8395e0ca9ac3d46dbfff87229e429ba6f102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb3abbc611ca1e2f1f76f19dfc89a9d1b21ec72f253f0e4722f4190bf5c5394d 0.600000000000 1403267 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": 944973, "vin": [ { "gen": { "height": 944963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb3abbc611ca1e2f1f76f19dfc89a9d1b21ec72f253f0e4722f4190bf5c5394d" } } ], "extra": [ 1, 245, 1, 155, 235, 44, 245, 90, 8, 95, 114, 4, 2, 128, 252, 223, 131, 149, 224, 202, 154, 195, 212, 109, 191, 255, 135, 34, 158, 66, 155, 166, 241, 2, 17, 0, 0, 0, 1, 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