Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5b37341c160b0fd19c39946dd6230286dedb7fd466281223b980f5b01bc2772

Tx prefix hash: 97e8b54cb9272caec8366eb6f4ce5645e2dd71eb7023f03664794bcf8f5af4c8
Tx public key: b9d650de2fd91cdae88cf8ff45d728031ecf5e407aba354bcbdb6e8f5cb349c9
Timestamp: 1733579086 Timestamp [UCT]: 2024-12-07 13:44:46 Age [y:d:h:m:s]: 00:113:21:41:21
Block: 1170030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81202 RingCT/type: yes/0
Extra: 01b9d650de2fd91cdae88cf8ff45d728031ecf5e407aba354bcbdb6e8f5cb349c9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 855cb17551831ddcf31897b674a08880af0b2cbf94e546facfda4a5330cdfcd0 0.600000000000 1655757 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": 1170040, "vin": [ { "gen": { "height": 1170030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "855cb17551831ddcf31897b674a08880af0b2cbf94e546facfda4a5330cdfcd0" } } ], "extra": [ 1, 185, 214, 80, 222, 47, 217, 28, 218, 232, 140, 248, 255, 69, 215, 40, 3, 30, 207, 94, 64, 122, 186, 53, 75, 203, 219, 110, 143, 92, 179, 73, 201, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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