Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03798e2b97989b4f17feb07890c183e605fbbe30d1667e2c0672a2bbc9305dbf

Tx prefix hash: 6d66ea96ffa927eac68cb525dfb36660de159b41fc92f5cfeaf8dc0f37bc3465
Tx public key: a7c6b8b490403c05e3537680f3cc01331fbfc77f8673b360cb96bf3a5abd95e3
Timestamp: 1718179340 Timestamp [UCT]: 2024-06-12 08:02:20 Age [y:d:h:m:s]: 00:308:14:17:51
Block: 1042468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220531 RingCT/type: yes/0
Extra: 01a7c6b8b490403c05e3537680f3cc01331fbfc77f8673b360cb96bf3a5abd95e302110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e28408aaa7bf8277e8f90e06d7469785ca13c6b79a19a882651adcbb51e17fe5 0.600000000000 1511397 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": 1042478, "vin": [ { "gen": { "height": 1042468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e28408aaa7bf8277e8f90e06d7469785ca13c6b79a19a882651adcbb51e17fe5" } } ], "extra": [ 1, 167, 198, 184, 180, 144, 64, 60, 5, 227, 83, 118, 128, 243, 204, 1, 51, 31, 191, 199, 127, 134, 115, 179, 96, 203, 150, 191, 58, 90, 189, 149, 227, 2, 17, 0, 0, 0, 11, 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