Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5f502b9a01fa8c0f77fe47b48d0749f621b3190cc58488b2cd83e0f1def39d

Tx prefix hash: 332895c2c1784f10ebbe80c4a43c7ba10701b0c928dcb80c5ac1b7a47c1a28ce
Tx public key: c1f7d2491321fb95af2f6224aaa1b680a5e33c1eba5fe6b1ca12858d4c6a36ae
Timestamp: 1706144634 Timestamp [UCT]: 2024-01-25 01:03:54 Age [y:d:h:m:s]: 01:312:01:22:25
Block: 942664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481867 RingCT/type: yes/0
Extra: 01c1f7d2491321fb95af2f6224aaa1b680a5e33c1eba5fe6b1ca12858d4c6a36ae02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ba1cb549b46b7552841c3b844d88f70a1ce0cbdd739dbfa12f7ffee93a77699 0.600000000000 1400840 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": 942674, "vin": [ { "gen": { "height": 942664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ba1cb549b46b7552841c3b844d88f70a1ce0cbdd739dbfa12f7ffee93a77699" } } ], "extra": [ 1, 193, 247, 210, 73, 19, 33, 251, 149, 175, 47, 98, 36, 170, 161, 182, 128, 165, 227, 60, 30, 186, 95, 230, 177, 202, 18, 133, 141, 76, 106, 54, 174, 2, 17, 0, 0, 0, 4, 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