Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e03735b8cd566f09f9d34192cd2af787530653dfa13b802ebd1567168ccdd5

Tx prefix hash: acb16b118cec3dcd6f1a4c1f0fb2fa9b8349e4a55d894acd03320cced5ed7e7b
Tx public key: 288b0c32aef81afcd0a0a4f33dc8c5ec89be4eb5dfe765dce8e10b4ca1d9d6a0
Timestamp: 1711442024 Timestamp [UCT]: 2024-03-26 08:33:44 Age [y:d:h:m:s]: 01:010:16:50:13
Block: 986630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268587 RingCT/type: yes/0
Extra: 01288b0c32aef81afcd0a0a4f33dc8c5ec89be4eb5dfe765dce8e10b4ca1d9d6a00211000000150011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f97f6fad1122132fe0038ca8691a7b8f6c2627a4b2ef03d0a4382d96843235a4 0.600000000000 1446861 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": 986640, "vin": [ { "gen": { "height": 986630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f97f6fad1122132fe0038ca8691a7b8f6c2627a4b2ef03d0a4382d96843235a4" } } ], "extra": [ 1, 40, 139, 12, 50, 174, 248, 26, 252, 208, 160, 164, 243, 61, 200, 197, 236, 137, 190, 78, 181, 223, 231, 101, 220, 232, 225, 11, 76, 161, 217, 214, 160, 2, 17, 0, 0, 0, 21, 0, 17, 5, 91, 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