Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50dfe7c85a0f7e464f795d10c0715c5c19c2b8dc191b37a5d3f64a1f56652d2c

Tx prefix hash: 0326dcf6bdb22c6b2c1d80a0ae0cdb4a0554fc98cd052af206761f2b15029c03
Tx public key: a41ad4b6842427645e742cb3974309f4d97b01ec8969092fe5760cbdc7bdf0e2
Timestamp: 1711412635 Timestamp [UCT]: 2024-03-26 00:23:55 Age [y:d:h:m:s]: 01:230:22:40:14
Block: 986384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423724 RingCT/type: yes/0
Extra: 01a41ad4b6842427645e742cb3974309f4d97b01ec8969092fe5760cbdc7bdf0e202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef1f4fffb01e98ad35fceeb8592a48534fe0473ee53e5dd05a232afd4e6e28ad 0.600000000000 1446613 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": 986394, "vin": [ { "gen": { "height": 986384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef1f4fffb01e98ad35fceeb8592a48534fe0473ee53e5dd05a232afd4e6e28ad" } } ], "extra": [ 1, 164, 26, 212, 182, 132, 36, 39, 100, 94, 116, 44, 179, 151, 67, 9, 244, 217, 123, 1, 236, 137, 105, 9, 47, 229, 118, 12, 189, 199, 189, 240, 226, 2, 17, 0, 0, 0, 4, 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