Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57caf7a99064813c43863806be8f28c9e1032ec46b93a37588dc09fa28159c01

Tx prefix hash: ff061d08b6e811ca79c289325b836a3faf9def5a32db4640c964d0e366574b11
Tx public key: 76a603cf92e1d7e65344bf20d2ba7a9382e6a2e8e1cb8413d7819504c08d2b6e
Timestamp: 1705268864 Timestamp [UCT]: 2024-01-14 21:47:44 Age [y:d:h:m:s]: 01:068:17:41:26
Block: 935407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310234 RingCT/type: yes/0
Extra: 0176a603cf92e1d7e65344bf20d2ba7a9382e6a2e8e1cb8413d7819504c08d2b6e02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5048a0281c1be955ccf066650f66378148e62f1618d9ef6904d92ecedccc6ed0 0.600000000000 1393423 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": 935417, "vin": [ { "gen": { "height": 935407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5048a0281c1be955ccf066650f66378148e62f1618d9ef6904d92ecedccc6ed0" } } ], "extra": [ 1, 118, 166, 3, 207, 146, 225, 215, 230, 83, 68, 191, 32, 210, 186, 122, 147, 130, 230, 162, 232, 225, 203, 132, 19, 215, 129, 149, 4, 192, 141, 43, 110, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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