Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc67de4660671193921ab9c7dab7e523f50ea839e48544cd5e631cacc8a5fc96

Tx prefix hash: 3cdd48269cbc70636176fcf1e61078bd78b181bda10bdbcb3d07bd58ffe68dec
Tx public key: 4e5389245d3b59deae34c87d7fabce4c9c7f71d0c217ab3df043c9d8c8770c7d
Timestamp: 1710729004 Timestamp [UCT]: 2024-03-18 02:30:04 Age [y:d:h:m:s]: 00:364:00:28:57
Block: 980716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260259 RingCT/type: yes/0
Extra: 014e5389245d3b59deae34c87d7fabce4c9c7f71d0c217ab3df043c9d8c8770c7d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc755fd7d6b05413e3f2511bbd79e9b07bd8da49c9c38989257c730844847fbe 0.600000000000 1440797 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": 980726, "vin": [ { "gen": { "height": 980716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc755fd7d6b05413e3f2511bbd79e9b07bd8da49c9c38989257c730844847fbe" } } ], "extra": [ 1, 78, 83, 137, 36, 93, 59, 89, 222, 174, 52, 200, 125, 127, 171, 206, 76, 156, 127, 113, 208, 194, 23, 171, 61, 240, 67, 201, 216, 200, 119, 12, 125, 2, 17, 0, 0, 0, 3, 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