Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0301c97027ca76196c842d51e900539771dd3eb2624bff0e34217f61ec1a6589

Tx prefix hash: a1385bc133832dd4e4a0db7dd1f090c2aecd2f803e8ce04c33ef32c1a65c2924
Tx public key: 47e7e4ae9b3da1f5e579b929f7d4860f54a1ba8c1cdb3d0943b6a8bb1bbbae20
Timestamp: 1730158744 Timestamp [UCT]: 2024-10-28 23:39:04 Age [y:d:h:m:s]: 00:146:07:54:09
Block: 1141719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104384 RingCT/type: yes/0
Extra: 0147e7e4ae9b3da1f5e579b929f7d4860f54a1ba8c1cdb3d0943b6a8bb1bbbae20021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9593f39d7e1e1bb35ce85223d2390de2b956fc71c217b0ce8417a3895fb86c8a 0.600000000000 1625536 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": 1141729, "vin": [ { "gen": { "height": 1141719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9593f39d7e1e1bb35ce85223d2390de2b956fc71c217b0ce8417a3895fb86c8a" } } ], "extra": [ 1, 71, 231, 228, 174, 155, 61, 161, 245, 229, 121, 185, 41, 247, 212, 134, 15, 84, 161, 186, 140, 28, 219, 61, 9, 67, 182, 168, 187, 27, 187, 174, 32, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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